Dynamically adjust start_block_number for XRPL Indexer to Prevent Indexing error due to online_delete#3
Open
ingenlabsltd wants to merge 4 commits intoflare-foundation:mainfrom
Open
Conversation
Author
|
Just gonna open this pull request in here.. Sometimes if I do xrpl verifier restart and the block isn't available anymore at the local node due to online_delete I manually need to adjust the start_block_number to prevent indexing error. This patch fixes it dynamically with certain block difference threshold to force use the latest start block number. -- The script assumes that you have already synced the node atleast 14 days of data and probably atleast 14 days of indexed data for it to trigger the update_start_block_number |
ingenlabsltd
changed the title
Use value of start_block_number
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.